Sync with react.dev @ bd87c394 #903
Conversation
Co-authored-by: artimath <ryanjhunter@gmail.com>
* Add sections to llms.txt * Also add sitemap footer
* Revamp useOptimistic docs * Updates from review * Edit down a bit * Updates from feedback * Updates from feedback * Updates from feedback * fml, forgot startTransition again * rm "prop" * feedback from @stephan-noel * feedback from @stephan-noel * update note
Removed an extraneous "a" from the text
* More claude stuff * more stuff from uee edit * revert
This commit fixes the wording of __Rendering__ explanation paragraph in the "components and hooks must be pure" page, according to the suggestion so that it's easier to understand without any confusion around effects relation.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
115.12 KB (🟡 +4.54 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
New Page Added
The following page was added to the bundle from the code in this PR:
| Page | Size (compressed) | First Load |
|---|---|---|
/llms.txt |
253 B |
115.37 KB |
Five Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load |
|---|---|---|
/404 |
129.04 KB (🟢 -1.71 KB) |
244.16 KB |
/500 |
129.05 KB (🟢 -1.71 KB) |
244.17 KB |
/[[...markdownPath]] |
131.83 KB (🟢 -1.7 KB) |
246.95 KB |
/errors |
129.29 KB (🟢 -1.71 KB) |
244.41 KB |
/errors/[errorCode] |
129.27 KB (🟢 -1.71 KB) |
244.39 KB |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.
| セキュリティ研究者は、悪意のある HTTP リクエストを作成して任意のサーバ関数 (Server Function) エンドポイントに対して送信することで、React がそれをデシリアライズする際に、サーバプロセスをハングさせて CPU を消費する無限ループを引き起こすことができることを発見しました。アプリが React のサーバ関数のエンドポイントを実装していない場合でも、React Server Components をサポートしている場合は脆弱性の影響を受ける可能性があります。 | ||
| **CVEs:** [CVE-2026-23864](https://www.cve.org/CVERecord?id=CVE-2026-23864) | ||
| **Base Score:** 7.5 (High) | ||
| **Date**: January 26, 2025 |
| }); | ||
| ``` | ||
|
|
||
| `useEffectEvent` accepts an `event callback` and returns an <CodeStep step={1}>Effect Event</CodeStep>. The Effect Event is a function that can be called inside of Effects without re-connecting the Effect: |
There was a problem hiding this comment.
"without re-connecting the Effect" は原文が悪いので意訳
| --- | ||
|
|
||
| ### Exposing `action` prop from components {/*exposing-action-props-from-components*/} | ||
| ### コンポーネントから `action` を props として公開する {/*exposing-action-props-from-components*/} |
There was a problem hiding this comment.
以前からの訳抜けでした、今回の更新部分と関係しているのでまとめて修正します
| [さらに例を見る](#usage) | ||
| ======= | ||
| Effect Events are a part of your Effect logic, but they behave more like an event handler. They always “see” the latest values from render (like props and state) without re-synchronizing your Effect, so they're excluded from Effect dependencies. See [Separating Events from Effects](/learn/separating-events-from-effects#extracting-non-reactive-logic-out-of-effects) to learn more. | ||
| エフェクトイベントはエフェクトのロジックの一部ですが、よりイベントハンドラに近いふるまいをします。常に最新のレンダー時の値（props や state など）が "見える" 一方で、エフェクトの再同期を起こさないため、エフェクトの依存配列には入れません。詳しくは[エフェクトからイベントを分離する](/learn/separating-events-from-effects#extracting-non-reactive-logic-out-of-effects)を参照してください。 |
Co-authored-by: honey32 <honey32@bearwapps.com>
10 participants
This PR was automatically generated.
Merge changes from react.dev at bd87c39
The following files have conflicts and may need new translations:
Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.
DO NOT SQUASH MERGE THIS PULL REQUEST!
Doing so will "erase" the commits from main and cause them to show up as conflicts the next time we merge.